Split test doesn't need to be executed per Python version#130147
Split test doesn't need to be executed per Python version#130147
Conversation
Not always. I've added that explicitly in #126936 as we usually can't install all dependencies when adding a new Python version to CI. E.g. for 3.12 we added a conditional imports and modified the test collection if sys.version_info >= (3, 12):
collect_ignore_glob = ["test_*.py"]Doing the collection with another version than the actual test run would thus fail. At the moment, this doesn't seem to be necessary for 3.13 (#129442). However, I believe it's safer to keep the previous implementation and run it for each supported Python version. |
…me-assistant#130147)" This reverts commit a8db25f.
|
Looks like it's safe after all. I just needed to disable an integraion in #129442: a0eaddc and it looks like the tests still pass. |
Breaking change
Proposed change
Collecting will always report all tests, so no need to run it per Python version
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: